Jadd Hatchen
Psygod9
D.E.F.I.A.N.C.E
211
   |
Posted - 2013.12.10 17:37:00 -
[1] - Quote
XxGhazbaranxX wrote:no one wants 10 million isk? Fix it for meh xD
How about 100 million? ;) j/k
Did you try entering game, disabling voice, hitting PS button, going to accessories menu and disabling then re-enabling headset/bluetooth accessory, then hitting PS button to return to game and re-enabling the voice?
|
Jadd Hatchen
Psygod9
D.E.F.I.A.N.C.E
224
|
Posted - 2013.12.12 21:09:00 -
[2] - Quote
XxGhazbaranxX wrote:every time I disable voice I get disconnected
Ok, I finally ran into this bug last night. It's one hell-of-a thing to have happen and it makes the game almost unplayable IMO.
First, I see that you have already found what is probably the culprit for the voice comms bug:
https://forums.dust514.com/default.aspx?g=posts&t=127245&find=unread
Second, I found that I didn't have to go to that extreme to fix my version of the same bug, apparently all I needed to do was step 1 in this list:
https://forums.dust514.com/default.aspx?g=posts&t=114369&find=unread
Third, another possible fix posted recently is this:
https://forums.dust514.com/default.aspx?g=posts&t=124422&find=unread
Now on to my theory crafting into what I believe I did at the time of the error that caused the issue to occur so that others may hopefully avoid it.
First, I was in a FW match as a squad leader and was hoping to coordinate some OS action on the enemy but had voice active in squad chat only at the time. So I swapped my active voice over to Team chat via selection in the team chat menu. It seemed to work, I got no responses, so I swapped back to squad voice... AND FATAL ERROR MESSAGE APPEARS (unfortunately I did not get the number recorded for this).
This causes my client to disconnect from the server (like Ghaz above) and I have to restart to get back into game. Only once I do, the mic no longer works! After fiddling around with things (but never re-installing or deleting any files) I discovered two things. One the fix that worked for me was the first one I pointed to above. Logging out of one character, logging into an alternate character, setting voice there, then logging out of that character and back into my main. Stuff works again.
Two, it seems that what causes this bug to occur is that when you swap from voice in one channel to voice in another channel, the software is NOT waiting for you to be fully "removed" from the voice in the first channel. Thus you end up in a state where you are semi-logged into voice in one channel, while trying to unsuccessfully enter into voice in a new channel. Because never successfully exited voice in the first channel, the second channel denies you access and you have no mic.
This seems to be a simple sort of timing issue with your implementation of the voice software you are using, CCP. Either that or some kinda improper pointing at voice stuff that is not being properly terminated and thus left pointing at who knows what and where.
This is a seriously harsh bug that is not easily fixed by the end user and NEEDS to be prioritized ASAP!
|